

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>U [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Glossary,Glossary U">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <div style="text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 0px;"><table cellspacing="0" cellpadding="0" border="0" style="border: none; border-spacing:0px;">
<tr style="text-align:left;vertical-align:top;">
<td valign="middle" width="32" style="width:32px;"><p class="p_Heading1"><a href="glossaryofterms.htm"><img src="glossary%20page.gif" width="29" height="29" border="0" alt="Glossary Page"></a></p>
</td>
<td valign="middle" width="641" style="width:641px;"><p class="p_Heading1"><span class="f_Heading1">~U~</span></p>
</td>
</tr>
</table>
</div>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="t(glossary).htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="v(glossary).htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_Glossaryitem"><span class="f_Glossaryitem">UML</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">The Unified Modeling Language, a notation and specification for modeling software systems in an Object-Oriented manner. You can read more about UML at the OMG home page or at our UML Tutorial.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">UML diagrams</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">Diagrams used to model different aspects of the system under development. They include various elements and connectors, all of which have their own meanings and purposes. UML 2.1 includes 13 diagrams: Use Case diagram, Activity diagram, State Machine diagram, Timing diagram, Sequence diagram, Interaction Overview diagram, Communication diagram, Package diagram, Class diagram, Object diagram, Composite Structure diagram, Component diagram and Deployment diagram.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">UML toolbox</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">The main toolbar running down the center of Enterprise Architect from which you can select model elements to insert into diagrams. This is also known as the Enterprise Architect UML </span><span class="f_UIControl">Toolbox</span><span class="f_Glossarytext"> and the Object Toolbar.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">uninterpreted</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A placeholder for a type or types whose implementation is not specified by the UML. Every uninterpreted value has a corresponding string representation.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">See also:</span><span class="f_Glossarytext"> any [CORBA]</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">usage</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A dependency in which one element (the client) requires the presence of another element (the supplier) for its correct functioning or implementation.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">use</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A connector that indicates that one element requires another to perform some interaction. The Usage relationship does not specify how the target supplier is used, other than that the source client uses it in definition or implementation.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">use case [class]</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A UML model element that describes how a user of the proposed system interacts with the system to perform a discrete unit of work. It describes and signifies a single interaction over time that has meaning for the end user (person, machine or other system), and is required to leave the system in a complete state: either the interaction completed or was rolled back to the initial state.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">See also:</span><span class="f_Glossarytext"> use case instance</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">use case diagram</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A </span><span class="f_Glossarytext">diagram</span><span class="f_Glossarytext"> that captures Use Cases and Actor interactions. It describes the functional requirements of the system, the manner in which outside things (Actors) interact at the system boundary, and the response of the system.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">use case estimation</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">The technique of estimating project size and complexity based on the number of Use Cases and their difficulty.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">use case instance</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">The performance of a sequence of actions being specified in a Use Case. An instance of a Use Case.</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext" style="font-style: italic;">See also</span><span class="f_Glossarytext">:</span><span class="f_Glossarytext"> Use Case class</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">use case model</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A model that describes a system's functional requirements in terms of Use Cases.</span></p>
<p class="p_Glossaryitem"><span class="f_Glossaryitem">utility</span></p>
<p class="p_Glossarytext"><span class="f_Glossarytext">A stereotype that groups global variables and procedures in the form of a Class declaration. The utility attributes and operations become global variables and global procedures, respectively. A utility is not a fundamental modeling construct, but a programming convenience.</span></p>




            </div>
          </div>
        </div>



</div>


</body>
</html>
